Set up the api and backend #24
Merged
+2,033
−58
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
September 29, 2026 14:00
Sorry for the humongous commit. With this commit, the server is now possible to run with "npm run server". The Api also returns the amount of games that is requested. However nothing is validated yet.
Some files has been renamed, and showed as empty files instead of being removed.
This adds a trycatch in the fillGame to ensure that if there is something that goes wrong, it won't return bad data. The rest seem fine. There might be some issues that are not accounted for yet, but we will fix them when we find them.
4 tasks
elinejaa
approved these changes
Oct 2, 2026
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pr adds:
i decided against using Zod for validation, as I originally thought would be great to have. Zod would make types stricter, and could thus ruin a lot of data because of a small error. Currently we have some leniency on how the data is returned, with some of the fields being "optional". Currently, I think that is the better approach for our application.
If you have some good arguments as to why we should have Zod, don't hesitate to let me know.
Closing: #14